Skip to content

fix: removing bom release section#2867

Merged
csviri merged 1 commit intomainfrom
source-bom
Jul 16, 2025
Merged

fix: removing bom release section#2867
csviri merged 1 commit intomainfrom
source-bom

Conversation

@csviri
Copy link
Copy Markdown
Collaborator

@csviri csviri commented Jul 16, 2025

No description provided.

@openshift-ci openshift-ci bot requested review from metacosm and xstefank July 16, 2025 15:39
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 16, 2025
@csviri csviri changed the title source bom fix: removing bom release section Jul 16, 2025
Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 16, 2025
@csviri csviri merged commit 12b1711 into main Jul 16, 2025
24 of 25 checks passed
@csviri csviri deleted the source-bom branch July 16, 2025 15:42
@metacosm
Copy link
Copy Markdown
Collaborator

metacosm commented Aug 4, 2025

Have you checked that releasing will still publish the BOM, because, iirc, it is not using the JOSDK parent?

@csviri
Copy link
Copy Markdown
Collaborator Author

csviri commented Aug 4, 2025

Have you checked that releasing will still publish the BOM, because, iirc, it is not using the JOSDK parent?

Hi yes, in final version it is using the release related plugins directly. It published the bom.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants